Dynamic print job routing in a distributed printing environment

ABSTRACT

Methods, systems, and devices are described for dynamic print job routing in a distributed printing environment. A data store may include a set of rules for dynamically determining an identified print job destination based on at least one characteristic of a print job generated by a print job source. A rules engine may be configured to receive a notification of the print job, identify the characteristic of the print job from the received notification, and apply the set of rules in the data store to the identified characteristic of the print job to dynamically determine an updated print job destination for the print job. The updated print job destination is associated with at least one printer.

CROSS REFERENCES

The present application claims priority from U.S. Provisional PatentApplication Ser. No. 61/394,264, which is incorporated herein byreference in its entirety for all it discloses.

BACKGROUND

Embodiments of the invention relate to computer network communication,and more particularly, printing in a dynamic roaming environment.Organizations often use a variety of computing devices. Various computersystems may use a thin-client or a virtual desktop display inconjunction with a centralized server or mainframe, and also usetraditional workstations and handheld devices.

A thin-client may be a computing device that includes hardware,software, or both in a client-server architecture network. However, sucha network may use a central server for processing and may transmit andreceive input and output over a network or other communication mediumestablished between the device and the remote server. In some examples,a thin-client device may run web browsers or remote desktop software,such that significant processing may occur on the server.

Printing in such environments may present a number of significantchallenges. Traditionally, print drivers are stored and maintained oneach device, and this can cause administrative overhead and maintenanceissues. The problem may be exacerbated with mobile thin-clients andother mobile devices, as the number of drivers that may need to bestored can increase substantially as more printers become available.

There are also challenges related to selecting the right printer andprint server in a dynamic environment. For example, with a mobile deviceor a roaming user, it may be a challenge to identify the appropriateprinters because of the legacy architecture for printing networks. Also,because of the traditional ways printer networks communicate, feedbackfor print jobs and identifying available printers can presentchallenges, as well. Thus, there may be a need in the art for novelsystem architectures to address one or more of these issues.

SUMMARY

Methods, systems, and devices are described for dynamic print jobrouting in a distributed printing environment.

In one set of embodiments, a distributed printing system includes aprint job source that generates a print job, multiple printers, a datastore, and a rules engine. The data store includes a set of rules fordynamically determining an updated print job destination for the printjob based on at least one characteristic of the print job. The rulesengine receives a notification of the print job, identifies the at leastone characteristic of the print job from the received notification, andapplies the set of rules in the data store to the identifiedcharacteristic(s) of the print job to dynamically determine an updatedprint job destination for the print job. The updated print jobdestination is associated with at least one of the printers.

In another set of embodiments, a method of dynamic print routing in adistributed printing environment includes receiving a notification of aprint job from a print job source, identifying at least onecharacteristic of the print job from the received notification; anddynamically determining an updated print job destination for the printjob based on the at least one characteristic of the print data. Theupdated print job destination is associated with at least one printer.

In another set of embodiments, a rules engine apparatus includes areceiving module, an identification module, and a destination updatingmodule. The receiving module receives a notification of a print job froma print job source. The identification module identifies at least onecharacteristic of the print job from the received notification of theprint job. The destination updating module dynamically determines anupdated print job destination for the print job based on the at leastone characteristic of the print job. The updated print job destinationis associated with at least one printer.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of the presentinvention may be realized by reference to the following drawings. In theappended figures, similar components or features may have the samereference label. Further, various components of the same type may bedistinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If only the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

FIG. 1 is a block diagram illustrating a system for distributed printingin a dynamic roaming and traditional static environments, according tovarious embodiments of the invention.

FIG. 2 is a block diagram illustrating a central server computer systemin a system for distributed printing in a dynamic roaming andtraditional static environments, according to various embodiments of theinvention.

FIG. 3 is a block diagram illustrating a data store in a system fordistributed printing in a dynamic roaming and traditional staticenvironments, according to various embodiments of the invention.

FIG. 4 is a block diagram illustrating a backend in a system fordistributed printing in a dynamic roaming and traditional staticenvironments, according to various embodiments of the invention.

FIG. 5 is a block diagram illustrating a logical path taken by printdata in a system for distributed printing in a dynamic roaming andtraditional static environments, according to various embodiments of theinvention.

FIG. 6 is a diagram illustrating an example of a system for dynamicprint job routing in a distributed printing environment, according tovarious embodiments of the invention.

FIGS. 7A, 7B, and 7C are diagrams illustrating tables which may bestored in a centralized data store of distributed printing environment,according to various embodiments of the invention.

FIGS. 8A, 8B, and 8C are diagrams illustrating tables which may bestored in a centralized data store of distributed printing environment,according to various embodiments of the invention.

FIG. 9 is a block diagram illustrating an example of a rules engine in adistributed printing environment, according to various embodiments ofthe invention.

FIG. 10 is a flowchart diagram illustrating an example of a method ofdynamic print job routing in a distributed printing environment,according to various embodiments of the invention.

FIG. 11 is a flowchart diagram illustrating an example of a method ofdynamic print job routing in a distributed printing environment,according to various embodiments of the invention.

FIG. 12 is a flowchart diagram illustrating an example of a method ofdynamic print job routing in a distributed printing environment,according to various embodiments of the invention.

FIG. 13 is a schematic diagram that illustrates a representative devicestructure that may be used in various embodiments of the presentinvention

DETAILED DESCRIPTION OF THE INVENTION

The present description sets forth examples of systems, methods, anddevices for dynamic print job routing in a distributed printingenvironment. In these systems, methods, and devices, a set of rules isstored in a data store for dynamically determining an updated print jobdestination for a print job based on at least one characteristic of theprint job. A rules engine receives a notification of the print job,identifies the characteristic(s) of the print job from the receivednotification, and applies the set of rules in the data store to theidentified characteristic(s) of the print job to dynamically determinethe updated print job destination for the print job. The print jobdestination is associated with a printer.

This description provides examples, and is not intended to limit thescope, applicability or configuration of the invention. Rather, theensuing description will provide those skilled in the art with anenabling description for implementing embodiments of the invention.Various changes may be made in the function and arrangement of elements.

Thus, various embodiments may omit, substitute, or add variousprocedures or components as appropriate. For instance, it should beappreciated that the methods may be performed in an order different thanthat described, and that various steps may be added, omitted orcombined. Also, aspects and elements described with respect to certainembodiments may be combined in various other embodiments. It should alsobe appreciated that the following systems, methods, devices, andsoftware may individually or collectively be components of a largersystem, wherein other procedures may take precedence over or otherwisemodify their application.

Systems, devices, methods, and software are described for dynamic printjob routing within a distributed printing environment. In one set ofembodiments, shown in FIG. 1, system 100 includes a central servercomputer system 105, a data store 110, print servers 145, and printers150. Each of these components may be in communication with each other,directly or indirectly.

The central server computer system 105 may include a rules engine 130, asession manager 135, and a print router 140. The central server computersystem 105 may be made up of one or more server computers, workstations,web servers, or other suitable computing devices. The central servercomputer system 105 may be fully located within a single facility ordistributed geographically, in which case a network may be used tointegrate different components.

The central server computer system 105 may receive a print job. Theprint job may be received from a windows session 125. Alternatively, theprint job may be received from an application session 115 via a backend120. The print job may also or alternatively be received from anapplication session 115 via a cloud computing environment (notspecifically shown). The print job may be received from thin-clients(e.g., SUN RAY clients available from Oracle Corporation, WYSE clientsavailable from Wyse Technology, etc.), thick clients (e.g., desktops,laptops), mobile devices, tablets, etc., although these devices are notspecifically shown in the diagram Moreover, the print job may bereceived from any type of desktop or virtual desktop environment.Examples of suitable desktop environments from which the print job maybe received include, but are not limited to, LINUX environments based onthe open-source Linux kernel; WINDOWS environments based on softwareavailable from Microsoft, Inc.; OS/X environments based on softwareavailable from Apple, Inc.; VMWARE virtual environments based onsoftware available from VMware, Inc.; CITRIX virtual environments basedon software available from Citrix Systems, Inc.; Windows TerminalServices/Remote Desktop virtual environments based on software availablefrom Microsoft, Inc.; ANDROID environments based on software availablefrom Google, Inc.; IOS environments based on software available fromApple, Inc.; WEBOS environments based on software available from HewlettPackard Company; combinations thereof; and the like. In someembodiments, the central server computer system 105 may receive noticeor identification for a print job, and perform the functionalitydescribed herein based on such notice or identification only.

A set of drivers may be stored at data store 110. Data store 110 may bea single database, or may be made up of any number of separate anddistinct databases. The data store 110 may include one, or more,relational databases or components of relational databases (e.g.,tables), object databases, or components of object databases,spreadsheets, text files, internal software lists, or any other type ofdata structure suitable for storing data. Thus, it should be appreciatedthat a data store 110 may each be multiple data storages (of the same ordifferent type), or may share a common data storage with other datastores. Although in some embodiments the data store 110 may be distinctfrom a central server computer system 105, in other embodiments it maybe integrated therein to varying degrees.

As noted above, notification of a requested print job may be received atthe central server computer system 105. A session manager 135 mayreceive the notification, and may assign a terminal identifier (TID) toa device requesting the job. The central server computer system 105 mayidentify information about the print job (e.g., identification andlocation of the applicable print server 145 and printer 150, andidentification of the proper driver). Drivers for the print job may betransmitted to the appropriate print server 145 and to the client devicerequesting the job. The drivers may be installed, and the device andprint server 145 may execute the print job with the installed drivers.Thus, the central server computer system 105 may access the data store110 to distribute drivers to the print server 145 or the device, andthus in some embodiments the drivers do not need to be maintained oneach device or print server 145. The drivers may be taken down oruninstalled after each job, set of jobs, or period with no use.

In some embodiments, the central server computer system 105 may use theinformation about a print job to identify an appropriate operatingsystem (OS) and print driver for the print server for a given print job.The central server computer system 105 may access the data store 110 toretrieve the OS and print driver, and load an OS in real-time inresponse to receiving a print job. The central server computer system105 may install the appropriate driver, thus creating a virtual printserver (which may, but need not be, print server 145). The virtual printserver executes the print job. After the print job is complete, thedriver and OS may be taken down. In alternative embodiments, printservers may not be dynamically generated in response to individual printjobs or at all. For example, the central server computer system 105 maydistribute incoming print jobs among a fixed set of physical or virtualprint servers 145.

In some embodiments, a printer 150 is selected (e.g., automatically orby a user). The print router 140 at the central server computer system105 may receive the selection. At the print router 140, the selectedprinter may be mapped to a 1) driver of a table of drivers, and 2) aprint server 145 of a table of print servers. A rules engine 130 at thecentral server computer system 105 may be used in the selection of theprinter. The rules engine 130 may be configured to dynamically map aprint job to a print server 145 and printer 150 for the print job. Byway of example, upon notification or receipt of the print job, the rulesengine 130 may access a set of rules to determine the correct printserver 145 and printer 150 for the print job. The rules may dynamicallymake this determination based on the location of the device. The type ofdevice, attributes of the print job, and other factors may be used bythe rules engine 130 to determine the correct type and location for theprint server 145 and printer 150.

It should be understood that the print servers 145 may be any real orvirtual machine or environment that hosts a print driver for controllinga printer 150. Thus, in certain examples a print server 145 may beimplemented by circuitry, logic, and/or software within the printer 150.Additionally or alternatively, a print server 145 may include a real orvirtual network server and/or a personal computing device incommunication with a printer 150.

In some embodiments, feedback from a printer 150 is received at theprint server 145, and then forwarded on to a print router 140. The printrouter 140 may route the feedback (e.g., job failed, out of ink, out ofpaper, etc.) to the client device. This report may be in the form of adialogue box. The feedback may be routed to avoid the backend 120, evenwhen the print job is initially routed through the backend 120. Inresponse to feedback from a print router 140, a client device may director route a print job. This routing may be to a new printer, or may callup alternative functionality (e.g., a new tray) for a printer that isalready in use. Thus, instead of unidirectional printing, print jobs(e.g., sent through a backend 120) may be controlled by two-waycommunication between the print router 140 and the device.

The components of the system 100 may be directly connected, or may beconnected via a network (not shown), which may be any combination of thefollowing: the Internet, an IP network, an intranet, a wide-area network(“WAN”), a local-area network (“LAN”), a virtual private network, thePublic Switched Telephone Network (“PSTN”), or any other type of networksupporting data communication between devices described herein, indifferent embodiments. A network may include both wired and wirelessconnections, including optical links. Many other examples are possibleand apparent to those skilled in the art in light of this disclosure. Inthe discussion herein, a network may or may not be noted specifically.If no specific means of connection is noted, it may be assumed that thelink, communication, or other connection between devices may be via anetwork.

Session manager 135 may include an API architecture which serves as thecommunication control point, managing virtual desktop sessions andbrokering sessions for clients to backend 120 virtual desktop andapplication sessions. The session manager 135 may broker and passthrough mechanisms for client devices to active virtual sessions. Thecentral server computer system 105 may include a centralized managementconsole (not shown), which may be a web-based management console forconfiguration, real time monitoring, and reporting. There may bemanagement capabilities for the entire virtual desktop/applicationenvironment.

FIG. 2 shows a block diagram of a central server computer system 105-a.The central server computer system 105-a may be one example of thecentral server computer system 105 in FIG. 1. The central servercomputer system 105-a shown in FIG. 2 includes a rules engine 130, asession manager 135, a print router 140-a, and a print server manager205. The rules engine 130 and the session manager 135 shown in FIG. 2may be substantially the same as the rules engine 130 and the sessionmanager 135 shown in FIG. 1. The print router 140-a may be one exampleof the print router 140 shown in FIG. 1.

The print router 140-a may match print jobs received from externalsessions 115, 125 to one or more destination printers 150 and/or printservers 145. To accomplish these tasks, the print router 140-a mayinclude at least a print data receiving module 210, a print sourceidentification module 215, a print parameters identification module 220,a printer destination identification module 225, and a printer feedbackrouting module 230.

The print data receiving module 210 may be configured to receive printdata corresponding to a print job from an external session 115, 125 viaa communication channel established by the session manager 135. Incertain embodiments, the print data received from the external session115, 125 may be in the form of one or more page description languages(PDLs). Examples of page description languages that may be received atthe receiving module 210 include, but are not limited to, PostScript,Portable Document Format (PDF), Printer Command Language (PCL), ScalableVector Graphics (SVG), Open XML Paper Specification (XPS), and any otherpage description language that may suit a particular implementation ofthe principles described herein.

In other embodiments, the print data received from the external session115, 125 may be in the form of text or images for use with a standardtemplate stored by a print server 145 or a printer 150. For example, theprint data may be used to print a personalized bracelet worn by apatient in a medical facility. In this example, the print data mayinclude text corresponding to the name of the patient, and the name ofthe patient's doctor. This text, when received by a print server 145 ora printer 150, may be applied to a standard bracelet template to print abracelet having the name of the patient and the name of the patient'sdoctor.

In additional or alternative embodiments, the print data received by theprint data receiving module 210 may be in the form of an image that hasalready been rasterized by the external session 115, 125 in preparationfor delivery to a printer 150.

The print data receiving module 210 may be configured to cache thereceived print data at a designated storage area. In certain examples,the designated storage area may be in a data store 110. The cached printdata may be accessible to the rules engine 130 or any other module orprocess.

The print source identification module 215 may be configured to analyzethe received print data to determine certain attributes orcharacteristics of the received print data. These attributes orcharacteristics may also be stored for use by the other modules orprocesses. For example, the print source identification module 215 mayassociate the received print data with a format in the data store 110.This format information may be available to the rules engine 130 for usein enforcing one or more rule sets.

In certain examples, the print source identification module 215 mayanalyze the print data received by the print data receiving module 210to determine a source of the print data. By way of example, the sourcemay be determined using information from the session manager 135,information acquired by the print data receiving module 210, and/orinformation attached to the print data itself by the source. Once theprint source has been identified, the identity of the print source maybe associated with the received print data. For example, the identity ofthe print source may be stored in the data store 110.

The print parameters identification module 220 may identify certainprint parameters for the received print data. These print parameters maybe included with the received print data and/or determined by logicaldeduction (e.g., using the rules engine 130). For instance, a user of anexternal session 115, 125 may specify a particular print parameter whichmay be transmitted to the central server computer system 105-a with theprint data or logically deduced from the received print data.Additionally or alternatively, certain default print parameters may bedetermined for the print data based on the identity of the source of theprint data and/or another attribute associated with the print data.

Examples of print parameters that may be identified by the printparameters identification module 220 include, but are not limited to, aselected type of printing media, a selected size of printing media, aselected source of printing media, an ink or toner color setting, acollation setting, a staple setting, a duplex setting, a scalingsetting, combinations thereof, and the like.

The printer destination identification module 225 may be configured toidentify an appropriate destination printer 150 and/or print server 145for print data received at the print data receiving module 210. Theprinter destination identification module 225 may identify theappropriate destination printer 150 based on one or more attributes ofthe print data. In certain examples, the printer destinationidentification module 225 may pass certain attributes of the print data(e.g., the identity and/or location of the source of the print datadetermined by the print source identification module 215, the printparameters determined by the print parameters identification module 220,etc.) to the rules engine 130.

The rules engine 130 may apply a certain set of predetermined ordynamically updated rules to the input it receives from the printerdestination identification module 225 to determine the destinationprinter 150 and/or print server 145 for the print data. The destinationprinter 150 and/or print server 145 determined by the rules engine 130may then be returned to the printer destination identification module225.

Once the destination printer 150 and/or print server 145 has beenidentified for the print data, the print data forwarding module 230 maybe configured to forward the print data on to the identified printer 150and/or print server 145. The print data may be forwarded over a localconnection and/or over a network or logical connection. Additionally, incertain examples, the print data forwarding module 230 may be configuredto receive feedback from a printer 150 and/or a print server 145 about aspecific print job and process the feedback and/or forward the feedbackto a third party, such as the source of that particular print job.

The print server manager 205 of the central server computer system 105-amay handle certain aspects related to the distribution of drivers forprinters to the print servers 145 and the general maintenance of theprint servers 145. Accordingly, the print server manager 205 may includea driver identification module 235, a driver deployment module 240, anoperating system identification module 245, and a print serverinstantiation module 250.

The driver identification module 235 may, in response to a set of printdata being assigned to a particular printer 150, determine anappropriate driver for that printer 150. As described above with regardto FIG. 1, the appropriate driver may be selected from a centralrepository of drivers stored, for example, at data store 110. The driveridentification module 235 may be further configured to determine whetheran appropriate driver for the selected printer 150 is already installedon a print server 145 chosen to send the print data to the selectedprinter 150. In certain examples, the driver identification module 235may compare a version of the driver stored by the chosen print server145 with a version of the driver stored at the central repository todetermine whether the driver stored by the chosen print server 145 iscurrent.

In the event that a determination is made that the chosen print server145 does not have the appropriate driver or a correct version of theappropriate driver, the driver deployment module 240 may install theappropriate driver on the print server 145. In certain examples, thedriver deployment module 240 may access and write to storage associatedwith the print server 145 via a local connection, network connection,and/or a logical connection to install the appropriate driver to theprint server 145.

The operating system identification module 245 may be configured toidentify an appropriate operating system associated with an appropriatedriver for the selected printer 150. In the event that a print server145 running the appropriate operating system and in communication withthe selected printer 150 does not exist or is unavailable, the printserver instantiation module 250 may instantiate a new print server 145.The newly instantiated print server 145 may be created on a dedicated orvirtual machine by loading the appropriate operating system to thededicated or virtual machine. In certain examples, an operating systemimage having the appropriate driver preinstalled may be used toinstantiate the new print server 145.

FIG. 3 is a block diagram of one example of a data store 110-a that maybe associated with a central server computer system 105. The data store110-a shown in FIG. 3 may be an example of data store 110 shown inFIG. 1. As shown in FIG. 3, data store 110-a may store drivers 305,libraries 310, device configurations 315, tables 320, rules 325, andoperating system images 330.

Data store 110-a may maintain a repository of drivers 305 for variousprinters 150 supported by a distributed printing system 100. Inaccordance with the description of FIGS. 1-2, as a print job is receivedat the central server computer system 105, the central server computersystem 105 may associate the print job with a specific printer 150,dynamically access the data store 110 to retrieve a driver 305appropriate for the specific printer, and provide the retrieved driver305 to a print server 145 associated with the specific printer.

Because the drivers 305 are stored centrally at data store 110-a,individual machines implementing sessions 115, 125 and individual printservers 145 need not store a local print driver for each printersupported by the system 100. Moreover, as updated versions of drivers305 become available, a network administrator may make the updatedversions available to each print server 145 in the system by simplyupdating the repository of drivers 305 stored at the data store 110-a,thereby avoiding the need to roll out driver updates to each printserver 145 separately.

The data store 110-a may also store software libraries 310. For example,the data store 110-a may store libraries 310 associated with the drivers305. In certain embodiments, the libraries 310 may include Dynamic-LinkLibrary (DLL) or Dynamic Shared Object (DSO) files that allow the printservers 145 to dynamically communicate with the sessions 115, 125 whichgenerate the print jobs sent to printers 150. Thus, where the centralserver computer system 105 provides a driver 305 to a print server 145for a specific printer 150, the central server computer system 105 mayinclude with the driver 305 one or more DLL files for that printer 150.The DLL(s) files may allow the print server 145 to provide feedback to asession 125 from which a print job originates in a way that isunderstandable to the session 125. For instance, if a user of thesession 125 generates the print job using a print Graphical UserInterface (GUI), the DLL transmitted to the print server 145 may allowthe print server 145 to provide feedback to the user of the session 125through the print GUI.

By way of example and not limitation, consider the case where a printjob generated by a session 125 has been sent to a print server 145 forprinting by a specific printer 150, and that the printer 150 is out ofpaper. The printer 150 may send a feedback message to the print server145 indicating that the printer 150 is out of paper, and the printserver 145 may provide this feedback message to a print dialog window inthe session 125 using a DLL received from the central server computersystem 105. This process may allow for a more seamless printingexperience for a user of session 125, despite the fact that the session125 may not locally store a print driver or DLL for communicating withthe printer 150.

In certain examples, the data store 110-a may also store deviceconfigurations 315, such as settings configurations for printers 150.Thus, when the central server computer system 105 transmits a print jobto a print server 145 associated with a specific printer 150, thecentral server computer system 105 may also include in the transmissiona configuration 315 retrieved from the data store 110-a for that printer150. The configuration 315 may specify, for example, settings such asprinter margin settings, duplex settings, paper tray settings, ink colorsettings, collation settings, and the like. The configuration 315transmitted to the print server 145 by the central server computersystem 105 may be specific to the printer 150, the session 115, 125generating the print job, and/or the character or content of the printjob itself.

Additionally, the data store 110-a may store and maintain various tables320. The tables 320 may reflect certain relationships present in thesystem 100. For example, the tables 320 may include one or more tables320 associating specific sessions 115, 125 with terminal identifiers ornode identifiers, one or more tables 320 associating specific sessions115, 125 with physical locations, one or more tables 320 associatingspecific printers 150 or print servers 145 with physical locations, oneor more tables 320 associating specific sessions 115, 125 with defaultprinters 150, and/or one or more tables 320 tracking any otherassociation in the system 100 that may suit a particular implementationof the principles described herein.

In certain examples, two or more of the tables 320 stored by the datastore 110-a may be interrelated in such a way that allows for logicaldeductions in routing print jobs to print servers 145 or other usefulpurposes. For instance, the data store 110-a may include: a) a firsttable 320 associating each terminal identifier at a port with aparticular session 115, 125 at a specific physical location; and b) asecond table 320 associating each physical location for a session 115,125 with a default printer 150. In this case, the information in thefirst table 320 and the second table 320 may be used by the centralserver computer system 105 to associate a print job received at a portwith a specific default printer 150.

The data store 110-a may also include one or more rules 325 for use bythe central server computer system 105 in routing received print jobs toprint servers 145 and printers 150. As noted above in the description ofFIGS. 1-2, the rules engine 130 of the central server computer system105 may be configured to dynamically map a print job to a print server145 and printer 150 for the print job by accessing the set of rules 325stored in the data store 110-a. The rules 325 may take into accountfactors such as the location of the device generating the print job, thetype of device generating the print job, attributes of the print job,and other factors. Some of these factors may be stored in the tables320.

Additionally, the data store 110-a may include one or more operatingsystem images 330. The operating system images 330 may be used, forexample, in the dynamic creation of print servers 145. As describedabove, certain drivers 305 may not be compatible with the standardoperating systems executed by typical print servers 145 in the system100. Accordingly, when a print job is indicated for a printer 150 usingone of these drivers 305, the central server computer system 105 mayretrieve a compatible operating system image 330 from the data store110-a and instantiate a new print server 145 by loading the operatingsystem image 330 onto a real or virtual machine. The newly instantiatedprint server 145 may then receive the print job from the central servercomputer system 105 and control the indicated printer 150 using theappropriate driver 305 to complete the print job.

Turning now to FIG. 4, a block diagram is shown of an illustrativebackend 120-a for use in a distributed printing system 100. The backend120-a shown in FIG. 3 may be an example of the backend 120 shown inFIG. 1. The backend 120-a may be configured to forward print data 405 toa next destination in the printing pipeline, such as a central servercomputer system 105, a print server 145, or a printer 150, as describedin more detail below. To accomplish this functionality, the backend 120may include a receiving module 410 to receive the print data 405 from anapplication session 115, a backend routing module 415 for determiningthe next destination of the print data 405, and a transmission module425 to transmit the print data 405 to the determined next destination.In some examples, the backend 120-a may also include a rasterizationmodule 420 for rasterizing the print data 405 prior to transmitting theprint data 405 to the central server computer system 105.

The receiving module 410 of the backend 120-a may be configured toreceive the print data 405 over a channel of communication with theapplication session 115. In some examples, the channel of communicationmay include one or more local connections (e.g., serial ports, parallelports, etc.) between the backend 120-a and a device implementing theapplication session 115. Additionally or alternatively, the channel ofcommunication may include one or more network connections (e.g.,Ethernet, WiFi, etc.) and/or logical connections (e.g., where thereceiving module 410 of the backend 120-a and the application session115 are implemented by the same physical machine).

In addition to receiving the print data 405, the receiving module 410may also identify the application session 115 providing the print data405. For example, the receiving module 410 may monitor a number of portsassociated with various application sessions 115. Each of theapplication sessions 115 may be assigned a terminal identifier or a nodeidentifier. Thus, when print data 405 is received, the receiving module410 may take note of the terminal identifier, the node identifier,and/or the port on which the print data is received to associate theprint data 405 with a known application session.

The backend routing module 415 may determine the next destination of theprint data 405 based on the application session 115 from which the printdata 405 was received. To this end, the destination identificationmodule 415 may maintain a table associating specific applicationsessions 115 with specific destinations. In certain examples, such as inthe system 100 of FIG. 1, all print data 405 received at the backend120-a, regardless of source, may be transmitted by the backend 120-a toa single central server computer system 105.

In alternative examples, the backend 120-a may be communicativelycoupled to a number of separate central server computer systems 105 suchthat print data 405 from different application sessions 115 istransmitted by the backend to different central server computer systems105. In additional or alternative examples, the backend 120-a may becommunicatively coupled to one or more central server computer systems105 in addition to one or more print servers 145 such that print data405 from some application sessions 115 is transmitted to a centralserver computer system 105 and print data 405 from other applicationsessions 115 is transmitted directly to a print server 145. In theseexamples, the backend routing module 415 may determine the nextdestination of each instance of print data 405 based on the applicationsession 115 from which the print data 405 was received.

In certain examples, the backend routing module 415 may further includelogic for dynamically determining in real-time how a print job is to berouted. For example, based on certain characteristics of the print data405, the backend routing module 415 may determine that it would be moreappropriate to forward the print data 405 to a central server computersystem 105 than to a print server 145 or printer 150. Additionally oralternatively, in examples where the backend 120-a is communicativelycoupled to multiple alternative central server computer systems 105, thebackend routing module 415 may perform load balancing in itsdistribution of different print jobs between the separate central servercomputer systems 105.

As mentioned above, in certain embodiments the backend 120-a may includea rasterization module 420. The rasterization module 420 may convert thereceived print data 405 into a raster image that can be understood by aprinter. In other embodiments, the print data 405 may already have beenrasterized by the application session 115 from which the print data 405was received. In still other embodiments, the print data 405 may berasterized at a print server 145 prior to printing.

The transmission module 425 of the backend 120-a may transmit thereceived print data 405 to the destination determined by the nextdestination identification module 415. This transmission may occur overone or more local connections (e.g., serial ports, parallel ports), oneor more network connections (e.g., Ethernet, WiFi), and/or one or morelogical connections (e.g., where the backend 120 and the nextdestination are implemented by the same physical machine).

FIG. 5 illustrates a diagram of one illustrative path 500 of print data405 through a distributed printing system. The print data 405 may firstbe generated and transmitted to a central server computer system 105-bby a session 125. The central server computer system 105-b may be anexample of the central server computer system 105 of FIG. 1 or FIG. 2.The session 125 may include an application executed by a host device. Incertain examples, a user of the application issues a command to printdata generated or hosted by the application.

In certain embodiments, the session 125 may transmit the print data 405directly to the central sever computer system 105-b. Alternatively, thesession 125 may utilize a backend 120 to transmit the print data 405 tothe central server computer system 105. The central server computersystem 105-b may perform session identification 510 to determine thesource of the print data 405. For example, the central server computersystem 105-b may look up a terminal identifier and/or a port associatedwith the print data 405 in a table to identify a device from which theprint data 405 originated.

Once the source of the print data 405 is known, the central servercomputer system 105-b may perform print routing 515 on the print data405 to select an appropriate printer 150-a for the print data 405. Theprinter 150-a may be an example of one of the printers 150 shown inFIG. 1. The print routing 515 may include applying a set of rules to oneor more parameters associated with the print data 405 and/or theidentified session 125. Additionally, the central server computer system105-b may retrieve 520 an appropriate driver 305-a for the identifiedprinter 150-a from a data store 110. The driver 305-a may betransmitted, together with the print data 405, from the central servercomputer system 105-b to a print server 145-a associated with theidentified printer 150-a. The print server 145-a may be an example ofthe print server 145 shown in FIG. 1. In certain examples, as describedabove, the print server 145-a may be dynamically instantiated inresponse to a particular printer 150-a being selected for the print data405.

The print server 145-a may install 530 the driver 305-a received fromthe central server computer system 105-b to enable the print server145-a to communicate with the selected printer 150-a. Additionally, theprint server may perform spooling 535 operations to receive and collectthe print data 405, scheduling 540 operations to schedule the print data405 for printing by the printer 150-a, and one or more conversion 545operations to transform the print data into a format understood by theprinter 150-a. In certain examples, the conversion 545 operations mayinclude rasterization of the print data 405. The print server 145-a maythen transmit the print data 405 to the selected printer 150-a over alocal connection, a network connection, and/or a logical connection forprinting.

It is worth noting that while an entire distributed printing system 100has been described as a whole for the sake of context, the presentspecification is directed to methods, systems, and apparatus that may beused with, but are not tied to the system 100 of FIGS. 1-5. Individualaspects of the present specification may be broken out and usedexclusive of other aspects of the foregoing description. This will bedescribed in more detail, below.

In one set of embodiments, systems, devices, methods, and software aredescribed for rules-based routing. A rules engine may be configured todynamically map a print job to a destination, such as a print server ora printer. Upon notification or receipt of the print job, the rulesengine may access a set of rules to determine the correct printer and/orprint server for the print job based on at least one characteristic ofthe print job. In certain examples, the rules engine may make thisdetermination based on the location of the print job source. The type ofprint source, attributes of the print job, and other factors may also beused by the rules engine to determine the correct print server and/orprinter for the print job.

FIG. 6 illustrates an example of a system 600 using a rules engine 130-afor dynamically routing print jobs in a distributed printingenvironment, according to various embodiments of the invention. Thesystem 600 includes a print job source 605, a rules engine 130-a, aprint router 140-c, and print job destinations 610. Each of thesecomponents may be in communication with each other, directly orindirectly. This system 600 may be an example of the systems 100 or 500described with reference to FIG. 1, or 5, and the rules engine 130-a andprint router 140-c may be a part of the central server computer system105 of FIG. 1 or 2. The print job source 605 may be an example of theuser sessions 115, 125 of FIG. 1, a device that hosts the users sessions115, 125 of FIG. 1, or another device that generates print data. Theprint job destinations 610 may be examples of the print servers 145 orthe printers 150 of FIG. 1 or 5.

The print job source 605 may transmit print data (not shown) for a printjob. The print data may include the image data for the print job and/ormetadata. The metadata may be indicative of one or more characteristicsof the print job. For example, the metadata may include an identifier ora type associated with the print job source 605, a location associatedwith the print job source 605, and other data. In other embodiments, theimage data may, in whole or in part, come from sources other than theprint job source 605.

The print data may be received by rules engine 130-a. In one example,the rules engine 130-a may evaluate the location of the print job source605, and may select the print job destination 610 for the print databased on this location. A variety of location-based technologies may beused to identify the print job source 605 location. When a user smoothroams to a new device and initiates a session, a collection program maybe initiated to collect location data to be sent to the rules engine130-a. By way of example, an update program may dynamically updateappropriate variables on a virtual desktop and/or application usersession to reflect a current user location, and other attributes. Insome embodiments, a program running on a device or a server (e.g., thecentral server computer system 105 of FIG. 1 or 3) may update the systemregistry and/or any other selected files with appropriate variables.

In other embodiments, the rules engine 130-a may evaluate additionalaspects of the print data, including, but not limited to, print source605 type, print data type, print source 605 identity, print dataidentity, print data content, print data size, and the like. The rulesengine 130-a may also evaluate additional factors, including but notlimited to time of day, printer status or availability, initial ordefault print job destination identity, and/or user preferences. Basedon the evaluation of the additional aspects of the print data and/or theother factors, the rules engine 130-a may apply a set of rules todynamically identify an updated print job destination 610 for the printjob. In still other embodiments, the print data may be associated withother types of addressing or identifiers, and the rules engine 130-a mayuse this information to dynamically identify a selected or default printjob destination 610. The rules engine 130-a may make this determinationfor each print job, for a set of print jobs, or periodically.

To dynamically determine the updated print job destination 610 for theprint data, the rules engine 130-a may access a data store 110-b storingvarious types of rules 325. The rules 325 may be used by the rulesengine 130-a to dynamically determine the specific print job destination610 based on at least one characteristic of the print job. The datastore 110-b may be an example of the data store 110 described above withrespect to FIG. 1 or 3. Additionally, the rules 325 stored by data store110-b may be examples of the rules 325 described above with respect toFIG. 3.

In the present example, the data store 110-b includes location rules325-a, device print job source rules 325-b, print job destination rules325-c, print job type rules 325-d, time of day rules 325-e, and userpreference rules 325-f In other examples, the data store 110-b may storemore or fewer categories of rules 325 for dynamically determining theprint job destination 610 for a print job. The different types of rules325 may be applied separately or in combination to determine aparticular updated print job destination 610. Thus, in certain examples,only one rule 325 may be used to dynamically determine an updated printjob destination 610 for a print job. Alternatively, multiple rules 325of the same or different types may be applied in series or in parallelto one or more characteristics of a print job to dynamically determinethe updated print job destination 610. By way of example, if differenttypes of rules applied to a print job conflict with each other, a set ofpriority rules may be used to resolve the conflict and definitivelydetermine the updated print job destination 610.

The location rules 325-a may allow for the dynamic selection of anupdated print job destination 610 based on a determined location of theprint job source 605 and/or a determined location of one or morepossible print job destinations 610. In some examples, the locationrules 325-a may allow for the dynamic selection of a print jobdestination 610 that is nearest to the print job source 605.

By way of example, the location rules 325-a may be configured to updatethe print job destination 610 of a print job by changing a previous ordefault print job destination 610 associated with the print job source605 based on a change in location by the print job source 605. Forinstance, where the print job source 605 is a user session 115 or 125 ona host device, the location rules 325-a may be configured to determinethat a user has logged into a new device associated with a new locationand dynamically change the print job destination 610 associated with thesession 115 or 125 to a print job destination 610-a (e.g., a printer150) that is closer to the new device.

Additionally or alternatively, where the print job source 605 is amobile device (e.g., a laptop computer or mobile phone), the locationrules 325-a may be configured to determine a print job destination 610-afor the mobile device based on a current location of the mobile device.The location of the mobile device may be identified using, for example,the known location of one or more network access points or other networkdevices with which the mobile device has associated, a GPS calculationperformed by the mobile device or a device known to be near the mobiledevice, a cellular base station triangulation calculation performed bythe mobile device or a device known to be near the mobile device, and/orany other method of the location that may suit a particular applicationof these principles.

The print job source rules 325-b in the data store 110-b may allow forthe dynamic determination of an updated print job destination 610 for aprint job based on at least one or more attributes of the print jobsource 605. The print job source rules 325-b may include, for example,rules based on an identity of the print job source 605 or an identifierassociated with the print job source 605. For example, a print jobsource 605 may be associated with one or more default print jobdestinations 610. By determining the identity of the print job source605, the rules engine 130-a may apply the print job source rules 325-bto identify a default print job destination 610 associated with thatprint job source 605.

In certain examples, the print job source 605 may be associated with aparticular level of security clearance and the print job source rules325-b may determine a print job destination 610 for a print job based onthe level of security clearance associated with the identity of theprint job source 605.

Additionally or alternatively, the print job source rules 325-b mayinclude rules based on the type of print job source 605. Thus, in someexamples different print job destinations 610 may be selected dependingon whether the print job source 605 is a session 115, 125 or a device.In other examples, different types of print job source 605 devices maybe associated with different print job destinations 610.

The print job destination rules 325-c in the data store 110-b may beused to determine a print job destination 610 for a print job based onthe status or identity of one or more possible print job destinations610. In one example, a print job destination rule 325-c may associate aprint job originally intended for a first print job destination 610-awith a different print job destination 610-e in response to adetermination that the first print job destination 610-a is busy, low onsupplies, experiencing technical problems, or otherwise unavailable.

In other examples, a print job destination rule 325-c may associate eachof the various print job destinations 610 with a security level andallow print jobs to be associated with a print job destination 610 ifsecurity requirements associated with the print job destination 610 aremet. In still other examples, a print job destination rule 325-c mayallow print jobs to be associated with a print job destination 610 onlyif certain security credentials are presented at the print jobdestination 610 by a recipient.

The print job type rules 325-d in the data store 110-b may allow for thedynamic determination of an updated print job destination 610 for aprint job based on a type associated with the print job. In certainexamples, the print job type rules 325-d may dynamically determine aprint job destination 610 for a print job of a certain type by matchingthe print job to a print job destination 610 capable of handling thattype of print job. For instance, a print job destination 610 for a labelprint job may be selected based on the ability of the print jobdestination 610 to accept and process label print jobs.

Additionally or alternatively, the print job type rules 325-d maydynamically determine print job destinations 610 based on the size ordifficulty of certain types of print jobs (e.g., sending large printjobs to less popular print destinations 610 to ease congestion at morepopular print destinations 610). In other examples, the print job typerules 325-d may enforce different levels of priority associated withdifferent types of print jobs. For instance, a print job for a label maybe given preferred access to a particular print job destination 610 withlabel printing capabilities over a print job for a generic document onstandard paper that can be printed by general-purpose printers.

In still other examples, the print job type rules 325-d may dynamicallydetermine print job destinations 610 for a print job based on securityconsiderations associated with the type of print job. For instance, theprint job type rules 325-d may not permit a type of print job associatedwith a certain level of security to be associated with a printer that iscommonly used by personnel who do not have authorization to view thecontents of that type of print job.

The time of day rules 325-e in the data store 110-b may be used todynamically determine an updated print job destination 610 for a printjob based on a current time of day. These time of day rules 325-e mayenforce policies put in place for individual distributed printingsystems 600. For instance, a security policy may permit a certain printjob destination 610 to receive print jobs at some times of the day, butnot at others (e.g., to prevent a confidential document from being leftin a printer tray overnight). Additionally or alternatively, the time ofday rules 325-e may be used to ease congestion. For example, where it isknown that a certain print job destination 610 is predictably congestedat certain times of the day, the time of day rules 325-e may divertprint jobs to alternate print job destinations 610 during those times ofthe day to lessen the burden on the congested print job destination 610.

The user preference rules 325-f of the data store 110-b may allow forthe dynamic determination of an updated print job destination 610 for aprint job based on a preference specified by a user associated with theprint job source 605. The preference may be an unsolicited preferencetransmitted with the print job from the print job source 605 (e.g., aprinter selection made at the time the print job is generated) orsolicited from the user. In one example, the rules engine 130-a mayreceive the print job, identify multiple possible print job destinations610 for the print job based on at least one characteristic of the printjob, provide the identified possible print job destinations 610 to theprint job source 605, receive a selection of one of the identifiedpossible print job destinations 610 from the print job source 605, anddynamically determine the updated print job destination 610 for theprint job based on the selection received from the print job source 605.

With the information identifying the dynamically selected print jobdestination 610, the print router 140-c may identify, for example, aparticular print server 145, a particular printer 150, and driver(s) 305associated with the selected printer 150 (e.g., if a printer 150 isselected, the print router 140-c may identify a print server 145 anddrivers 305 to be used for the print server 145 and the print job source605). The drivers 305 may be retrieved and distributed to the printserver 145 (e.g., by the print router 140-c or another server, such asthe central server computer system 105 of FIG. 1 or 3), and the drivers305 may be installed.

The print router 140-c may transmit or otherwise provide the print datato an identified print server 145 (note, however, that the print server145 may be a virtual print server, and thus in some embodiments both theprint router 140-c and print server 145 may be part of the centralserver computer system 105 of FIG. 1 or 3). A print server 145 mayprocess and format the print data, and transmit the processed data to aprinter 150 for printing.

In one set of embodiments, a set of tables may be stored in a data store(e.g., data store 110 of FIG. 1, 3, or 6) to track associations betweenprint job sources (e.g., print job source 605 of FIG. 6),characteristics associated with the print job (e.g., locations) andprint job destinations (e.g., print destinations 610 of FIG. 6). A rulesengine (e.g., rules engine 130 of FIG. 1, 2, or 6) may determine thelocation of a print job source, and map the print job source to anupdated print job destination based on the determination. FIGS. 7A, 7B,7C illustrate one such set of tables.

FIG. 7A illustrates a first table 705 that associates a virtual printeridentifier with a terminal identifier, a terminal identifier port, and adevice. The virtual printer identifier may identify a virtual printdestination initially associated with a print job received at centralserver computer system (e.g., central server computer system 105 of FIG.1 or FIG. 2) from a print job source. The terminal identifier mayidentify the print job source. A rules engine (e.g., rules engine 130 ofFIG. 1, 2, or 6) may determine the identity of a device associated withthe print job source. The first table 705 shows an inference by therules engine that the print job transmitted to virtual printer ID VPRT01by terminal ID L184001 on port 9100 is associated with device DTU-1.

FIG. 7B illustrates a second table 710 of possible print jobdestinations for a print job from terminal ID L184001 associated withdevice DTU-1. The second table 710 may be dynamically generated by arules engine based at least on the location of device DTU-1.Alternatively, the second table 710 may be continuously stored in a datastore and updated from time to time as changes to the rules engineand/or the system architecture occur. As shown in FIG. 7B, the possibleprint job destinations for the print job of the present example includethree printers, each of which is identified by a printer name. Thesecond table 710 may further associate each of the printers with alocation and a function. Additionally, the second table 710 indicates adefault printer (Dell_F1) for the print job from terminal ID L184001 ondevice DTU-1.

FIG. 7C illustrates a third table (715) which maps a print job receivedfrom terminal ID L184001 associated with device DTU-1 at port 9100 todefault printer Dell_F1. This mapping may be performed by the rulesengine to dynamically update the print destination of the print job, andmay occur on a per-print job basis.

FIGS. 8A, 8B, and 8C illustrate the set of tables 705, 710, 715 of FIGS.7A, 7B, and 7C, respectively, after the print source corresponding toterminal identifier L184001 has moved from device DTU-1 to device DTU-2.This move may occur, for example, if a user associated with terminalidentifier L184001 logs off of device DTU-1 and logs in to DTU-2, or ifa session associated with terminal identifier L184001 transitions fromnetwork access point DTU-1 to network access point DTU-2.

FIG. 8A illustrates the first table 705-a, as updated to reflect the newassociation of virtual printer identifier VPRT01, the print sourcecorresponding to terminal identifier L184001, and port 9100 with deviceDTU-2.

FIG. 8B illustrates the second table 710-a as updated to reflect theselection of a new default printer (HP_F3) for the print source, asdynamically assigned by a rules engine based on the location of DTU-2.The default printer for the print source may be dynamically updated tothe new default printer shown in FIG. 8B in response to the rules engineor a related module receiving a notification of a print job from theprint source.

FIG. 8C illustrates the third table 715-a as updated to reflect a newmapping of a print job received from the print source corresponding toterminal identifier L184001 and port 9100 to printer (HP_F3).

The tables 705, 710, 715 of FIG. 7 and FIG. 8 may be updated dynamicallyto reflect printer availability, printer backlog, and use patterns at agiven printer. The tables 705, 710, 715 may be generated or maintainedon a per-user, or class of user, basis. In other tables, additionalfactors may be considered, such as time of day, time of week, type ofdocument, application type, user type, and so on.

FIG. 9 illustrates an example of a rules engine 130-b that may be usedfor dynamic print job routing in a distributed printing environment. Therules engine 140-d may be an example of the rules engine 130 describedabove with respect to FIG. 1, 2, or 6. The rules engine 130-b of thepresent example includes a receiving module 905, an identificationmodule 910, and a destination updating module 915. Each of thesecomponents may be in communication, directly or indirectly.

The receiving module 905 may include logic configured to receive anotification of a print job. In certain examples, the notification ofthe print job may be received from a print job source (e.g., session115, 125 of FIG. 1, print job source 605 of FIG. 6). The notification ofthe print job may include the print job itself. Alternatively, thenotification of the print job may include a notification of the printjob, but not the print job itself.

The identification module 910 may include logic configured to identifyat least one characteristic of the print job from the notification ofthe print job received at the receiving module 905. The identifiedcharacteristic(s) of the print job may include one or more of a varietyof attributes associated with the print job. For example, thecharacteristic(s) of the print job may include location information,such as location information associated with a print job source,including information regarding a change in print job source location.

Additionally or alternatively, the characteristic(s) of the print jobmay include information regarding the type of print job, time of day,security permissions and policies, the identity of the print job source,the identity of a device generating the print data, and/or otherinformation about the print job. In certain examples, thecharacteristic(s) of the print job may include information regarding oneor more possible print job destinations (e.g., print servers 145 of FIG.1, 5, or 6, printers 150 of FIG. 1, 5, or 6). The information regardingthe one or more possible print job destinations may include, but is notlimited to, information regarding user preferences for print jobdestinations, information regarding the status of one or more possibleprint job destinations, information regarding default print jobdestinations, and the like.

In certain examples, the identification module 910 may communicate withan external entity to identify the one or more characteristic(s) of theprint job. For example, the identification module 910 may identify aninitial set of possible print job destinations for the print job basedon the received notification of the print job, provide the set ofpossible print job destinations to the print job source, and receive aselection of one of the possible print job destinations from the printjob source.

The destination updating module 915 may include logic for enforcing aset of one or more rules in a data store (e.g., data store 110 of FIG.1, 3, or 6) to dynamically determine an updated print job destinationfor the print job based on the identified characteristic(s) of the printjob.

In certain examples, the destination updating module 915 may dynamicallydetermine the updated print job destination for the print job based onthe location of the print job source. The updated print job destinationmay be, for example, a print job destination that is geographicallyclosest to the print job source or to a user of the print job source. Incertain examples, the destination updating module 915 may dynamicallydetermine the updated print job destination in response to adetermination that the location of the print job source has changed.

Additionally or alternatively, the destination updating module 915 maydynamically determine the updated print job destination based on thetype of the print job, a status of at least one possible print jobdestination for the print job, a current time of day, a user preference,security permissions and policies, the identity of the print job source,the identity of a device generating the print data, and/or othercharacteristic(s) of the print job.

In certain examples, the destination updating module 915 may replace aprevious print job destination associated with the print job with theupdated print job destination. The previous print job destination maybe, for example, a default print job destination or a virtual print jobdestination associated with the print job. In certain examples,replacing the previous print job with the updated print job may includechanging the default print job destination for the print job source.

FIG. 10 illustrates an example of a method 1000 of dynamic print jobrouting in a distributed printing environment. The method 1000 may beperformed, for example, by the central server computer system 105 of 1,2, or 5, the rules engine 130 of FIG. 1, 2, or 6, or the print router140 of FIG. 1, 2, or 5. At block 1005, a notification of a print job isreceived from a print job source. At block 1010, at least onecharacteristic of the print job is identified from the receivednotification. At block 1015, an updated print job destination isdynamically identified for the print job based on the at least oneidentified characteristic.

FIG. 11 illustrates an example of another method 1100 of dynamic printjob routing in a distributed printing environment. The method 1100 maybe performed, for example, by the central server computer system 105 of1, 2, or 5, the rules engine 130 of FIG. 1, 2, or 6, or the print router140 of FIG. 1, 2, or 5. At block 1105, a notification of a print jobhaving a first print job destination is received. The first print jobdestination may be a default print job destination, a virtual print jobdestination, and/or a print job destination preliminarily selected forthe print job. At block 1110, at least one characteristic of the printjob is identified from the received notification. At block 1115, a printserver destination is dynamically identified for the print job based onthe identified characteristic(s) of the print job. At block 1120, thedestination of the print job is updated to the identified print serverdestination. The destination of the print job may be updated byreplacing the first print job destination with the identified printserver destination. At block 1125, the print job is transmitted to theidentified print server destination.

FIG. 12 illustrates an example of another method 1200 of dynamic printjob routing in a distributed printing environment. The method 1200 maybe performed, for example, by the central server computer system 105 of1, 2, or 5, the rules engine 130 of FIG. 1, 2, or 6, or the print router140 of FIG. 1, 2, or 5. At block 1205, a notification of a print jobhaving a first virtual print job destination is received. At block 1210,at least one characteristic of the print job is identified from thereceived notification. At block 1215, an updated print job destinationis dynamically determined for the print job based on the identifiedcharacteristic(s). At block 1220, the virtual first destination of theprint job is replaced with the updated print job destination. At block1225, the print job is transmitted to the second print job destination.

The functionality of the central server computer system 105 of 1, 2, or5, the rules engine 130 of FIG. 1, 2, or 6, the print router 140 of FIG.1, 2, or 5, the backend 120 of FIG. 1 or 4, or the print server 145 ofFIG. 1, 5, or 6, may, individually or collectively, be implemented withone or more Application Specific Integrated Circuits (ASICs) adapted toperform some or all of the applicable functions in hardware.Alternatively, the functions may be performed by one or more otherprocessing units (or cores), on one or more integrated circuits. Inother embodiments, other types of integrated circuits may be used (e.g.,Structured/Platform ASICs, Field Programmable Gate Arrays (FPGAs), andother Semi-Custom ICs), which may be programmed in any manner known inthe art. The functions of each unit may also be implemented, in whole orin part, with instructions embodied in a memory, formatted to beexecuted by one or more general or application-specific processors.

A device structure 1400 that may be used for one or more components ofthe central server computer system 105 of 1, 2, or 5, the rules engine130 of FIG. 1, 2, or 6, the print router 140 of FIG. 1, 2, or 5, thebackend 120 of FIG. 1 or 4, the print server 145 of FIG. 1, 5, or 6, orfor other computing devices or printers described herein, is illustratedwith the schematic diagram of FIG. 13.

This drawing broadly illustrates how individual system elements of eachof the aforementioned devices may be implemented, whether in a separatedor more integrated manner. Thus, any or all of the various components ofone of the aforementioned devices may be combined in a single unit orseparately maintained and can further be distributed in multiplegroupings or physical units or across multiple locations. The examplestructure shown is made up of hardware elements that are electricallycoupled via bus 1305, including processor(s) 1310 (which may furthercomprise a digital signal processor (DSP) or special-purpose processor),storage device(s) 1315, input device(s) 1320, and output device(s) 1325.The storage device(s) 1315 may be a machine-readable storage mediareader connected to any machine-readable storage medium, the combinationcomprehensively representing remote, local, fixed, or removable storagedevices or storage media for temporarily or more permanently containingcomputer-readable information. The communications system(s) interface1345 may interface to a wired, wireless, or other type of interfacingconnection that permits data to be exchanged with other devices. Thecommunications system(s) interface 1345 may permit data to be exchangedwith a network.

The structure 1300 may also include additional software elements, shownas being currently located within working memory 1330, including anoperating system 1335 and other code 1340, such as programs orapplications designed to implement methods of the invention. It will beapparent to those skilled in the art that substantial variations may beused in accordance with specific requirements. For example, customizedhardware might also be used, or particular elements might be implementedin hardware, software (including portable software, such as applets), orboth.

It should be noted that the methods, systems and devices discussed aboveare intended merely to be examples. It must be stressed that variousembodiments may omit, substitute, or add various procedures orcomponents as appropriate. For instance, it should be appreciated that,in alternative embodiments, the methods may be performed in an orderdifferent from that described, and that various steps may be added,omitted or combined. Also, features described with respect to certainembodiments may be combined in various other embodiments. Differentaspects and elements of the embodiments may be combined in a similarmanner. Also, it should be emphasized that technology evolves and, thus,many of the elements are exemplary in nature and should not beinterpreted to limit the scope of the invention.

Specific details are given in the description to provide a thoroughunderstanding of the embodiments. However, it will be understood by oneof ordinary skill in the art that the embodiments may be practicedwithout these specific details. For example, well-known circuits,processes, algorithms, structures, and techniques have been shownwithout unnecessary detail in order to avoid obscuring the embodiments.

Also, it is noted that the embodiments may be described as a processwhich is depicted as a flow diagram or block diagram. Although each maydescribe the operations as a sequential process, many of the operationscan be performed in parallel or concurrently. In addition, the order ofthe operations may be rearranged. A process may have additional stepsnot included in the figure.

Moreover, as disclosed herein, the term “memory” or “memory unit” mayrepresent one or more devices for storing data, including read-onlymemory (ROM), random access memory (RAM), magnetic RAM, core memory,magnetic disk storage mediums, optical storage mediums, flash memorydevices or other computer-readable mediums for storing information. Theterm “computer-readable medium” includes, but is not limited to,portable or fixed storage devices, optical storage devices, wirelesschannels, a sim card, other smart cards, and various other mediumscapable of storing, containing or carrying instructions or data.

Furthermore, embodiments may be implemented by hardware, software,firmware, middleware, microcode, hardware description languages, or anycombination thereof. When implemented in software, firmware, middlewareor microcode, the program code or code segments to perform the necessarytasks may be stored in a computer-readable medium such as a storagemedium. Processors may perform the necessary tasks.

Having described several embodiments, it will be recognized by those ofskill in the art that various modifications, alternative constructions,and equivalents may be used without departing from the spirit of theinvention. For example, the above elements may merely be a component ofa larger system, wherein other rules may take precedence over orotherwise modify the application of the invention. Also, a number ofsteps may be undertaken before, during, or after the above elements areconsidered. Accordingly, the above description should not be taken aslimiting the scope of the invention.

1. A distributed printing system comprising: a print job sourceconfigured to generate a print job; a plurality of printers; a datastore comprising a set of rules for dynamically determining an updatedprint job destination for the print job based on at least onecharacteristic of the print job; and a rules engine configured to:receive a notification of the print job; identify the at least onecharacteristic of the print job from the received notification; andapply the set of rules in the data store to the identified at least onecharacteristic of the print job to dynamically determine the updatedprint job destination for the print job, wherein the updated print jobdestination is associated with at least one printer in the plurality ofprinters.
 2. The system of claim 1, wherein the rules engine is furtherconfigured to: identify a location of the print job source as the atleast one characteristic of the print job; and determine the updatedprint job destination based on the location of the print job source. 3.The system of claim 1, wherein the rules engine is further configuredto: determine a time of day associated with the print job; and determinethe updated print job destination based on the time of day associatedwith the print job.
 4. The system of claim 1, wherein the rules engineis further configured to: determine that the print job is of a certaintype; and determine the updated print job destination based on the typeof the print job.
 5. The system of claim 1, wherein the rules engine isfurther configured to: determine a status of at least one possible printjob destination; and determine the updated print job destination basedon the status of the at least one possible print job destination.
 6. Thesystem of claim 1, wherein the rules engine is further configured toreplace a print job destination previously associated with the print jobwith the updated print job destination.
 7. A method of dynamic printrouting in a distributed printing environment, comprising receiving anotification of a print job from a print job source; identifying atleast one characteristic of the print job from the receivednotification; and dynamically determining an updated print jobdestination for the print job based on the at least one characteristicof the print data, wherein the updated print job destination isassociated with at least one printer.
 8. The method of claim 7, whereinthe dynamically determining the updated print job destination for theprint job is performed by a rules engine configured to enforce a set ofrules stored in a data store.
 9. The method of claim 7, furthercomprising: identifying a location of the print job source as the atleast one characteristic of the print job; and determining the updatedprint job destination based on the location of the print job source. 10.The method of claim 9, further comprising: determining that the locationof the print job source has changed; and dynamically determining theupdated print job destination for the print job in response to thedetermination that the location of the print job source has changed. 11.The method of claim 7, further comprising: determining that the printjob is of a certain type; and determining the updated print jobdestination based on the type of the print job.
 12. The method of claim7, further comprising: determining a status of at least one possibleprint job destination; and determining the updated print job destinationbased on the status of the at least one possible print job destination.13. The method of claim 7, further comprising: determining a currenttime of day; and determining the updated print job destination based onthe current time of day.
 14. The method of claim 7, further comprising:replacing a previous print job destination associated with the print jobwith the updated print job destination.
 15. The method of claim 7,wherein the previous print job destination comprises a virtual print jobdestination.
 16. The method of claim 7, further comprising: changing adefault print job destination associated with the print job source. 17.The method of claim 7, further comprising: determining a plurality ofpossible print job destinations based on the at least one characteristicof the print job; providing the plurality of possible print jobdestinations to the print job source; receiving a selection of one ofthe plurality of possible print job destinations from the print jobsource; and determining the updated print job destination based on theselection received from the print job source.
 18. The method of claim 7,wherein the updated print job destination comprises at least one of aprint server or a printer.
 19. A rules engine apparatus, comprising: areceiving module configured to receive a notification of a print jobfrom a print job source; an identification module configured to identifyat least one characteristic of the print job from the receivednotification; and a destination updating module configured todynamically determine an updated print job destination for the print jobbased on the at least one characteristic of the print job, wherein theupdated print job destination is associated with at least one printer.20. The rules engine apparatus of claim 19, wherein the rules engineapparatus is implemented by at least one central server computer system.